Coridon is right in that it doesn't find any files other some subfolders of
POV-Ray.  Can't even get the main folder to be seen by adding a
Library_Path=C:\Program Files\POV-Ray for Windows v3.5

If the file is in the include subfolder all is fine.

Looking at the POV-Win Help I see it might be possible to use any path:

1.10.11.3.3 Open "filename"

Whenever you open the context menu, the editor first looks underneath the
edit caret to see if there is a line that looks like a POV-Ray scene file
'#include' directive. If one is found, the name of the specified file is
placed into the menu in place of "filename". If one is not found, then it
may show "Copy ... to Command-Line" (see below).
If you then select this command, the editor will attempt to find and open
the file in a new edit window. The standard include paths (as defined in
PVENGINE.INI) will be searched if the file is not found relative to the
current directory.



"standard" implies otherwise, such that the following is the part "defined
in pvengine.ini":

[Permitted Input Paths]
1=%INSTALLDIR%
2=C:\WINDOWS\Fonts


I'd think it meant to say povray.ini where the Library_Path= lines are
normally located instead.  Other than that I don't see a place designating
it there.  Could someone please demystify this for us?

--
text{ttf"arial","bob h",.1,0pigment{rgb 9}translate<-1,-.2,3>}


"Coridon Henshaw" <che### [at] sympaticoca> wrote in message
news:Xns### [at] 204213191226...
> "Thorsten Froehlich" <tho### [at] trfde> wrote in
> news:3c1ea704$1@news.povray.org:
>
> > The proper solution is to add a matching library_path "C:\temp\".
>
> Uhh, I just reported that the open function won't honor library_paths
which
> point to anywhere other than the default include directory.  As far as I
> can tell there is no workaround for either of the two bugs.

Post a reply to this message